| 3 | Approval of the Agenda | |
|---|---|---|
| R3-241501 | RAN3#123bis Meeting Agenda | RAN3 Chair |
| 4 | Approval of the minutes from previous meetings | |
| R3-241502 | RAN3#123 Meeting Report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-241503 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs |
| R3-241629 | Comments on the current way of working in RAN3 | Ericsson |
| R3-242103 | Response on R3-241629 | RAN3 Chair (ZTE) |
| 7 | General, protocol principles and issues | |
| R3-241504 | TR 30.531 v1.51.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| R3-241648 | TR 30.531 v1.51.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| 8.1 | New Incoming LSs | |
| R3-241505 | LS on area scope handling for QoE measurement collection | CT1(Ericsson) |
| R3-241506 | LS on Rel-18 RedCap enhancements work | CT1(Huawei) |
| R3-241507 | LS reply on defining new GTP-U Extension Header for PDU Set related information | CT4(Ericsson) |
| R3-241513 | Reply LS on area scope handling for QoE measurements | RAN2(Ericsson) |
| R3-241515 | Reply LS on issues with Packet Uu Loss Rate with delay threshold in the DL per DRB per UE | RAN2(Samsung) |
| R3-241516 | Reply LS on SPR | RAN2(Nokia) |
| R3-241517 | Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | RAN2(Huawei) |
| R3-241520 | LS Reply to SA5 on LS on new definitions of energy efficiency and energy consumption | SA2(OPPO) |
| R3-241522 | LS on per UE energy consumption in RAN | SA2(Vodafone) |
| R3-241524 | Clarification on the requirements for NTZ | SA2(LGE) |
| R3-241525 | Reply LS RP-240031 on clarification on requirements for NTZ. | TSG RAN(Interdigital) |
| R3-241526 | Reply LS RP-240029 on per UE energy consumption in RAN | TSG RAN(Interdigital) |
| 8.3 | Left over LSs / pending actions | |
| R3-241514 | Reply LS on RedCap UE MBS Broadcast reception | RAN2(Nokia) |
| R3-241659 | MBS FSAI for Redcap and non-Redcap UEs | Nokia |
| R3-241660 | Response LS on Redcap UE MBS Broadcast Reception | Nokia |
| R3-241661 | Switch to RRC Connected after SDT Partial Context Transfer | Nokia, Ericsson |
| R3-241662 | Correction of switch to RRC connected after SDT Partial Context Transfer | Nokia, Ericsson |
| R3-241663 | Correction of switch to RRC connected after SDT Partial Context Transfer | Nokia, Ericsson |
| R3-241664 | Response LS on SDT signalling optimization for partial context transfer | Nokia, Ericsson |
| R3-241668 | Consideration on SDT RAN2 solution and Network based solution | Huawei |
| R3-241669 | SDT RRC Release with resume indication [SDT_ReleaseEnh] | Huawei, Qualcomm Incorporated, Lenovo, ZTE, LG Electronics |
| R3-241670 | [DRAFT] Reply LS on SDT signalling optimization for partial context transfer | Huawei |
| R3-241671 | Consideration on RedCap UE MBS Broadcast reception | Huawei |
| R3-241672 | RedCap UE MBS Broadcast reception [RedcapMBS] | Huawei, CBN, Qualcomm Incorporated, ZTE |
| R3-241673 | [DRAFT] Reply LS on RedCap UE MBS Broadcast reception | Huawei |
| R3-241693 | Discussion on RRC release for SDT termination | ZTE, China Telecom, China Unicom |
| R3-241694 | Correction on SDT RRC Release with resume indication [SDT_ReleaseEnh] | ZTE, Huawei, China Telecom, Qualcomm, LG Electronics, China Unicom |
| R3-241856 | [Draft] Reply LS on SDT signalling optimization for partial context transfer | ZTE |
| R3-241924 | Discussion about SA2 and RAN2 LS on common FSA ID for RedCap UE | ZTE |
| R3-242069 | Further discussion related to Reply LS on improved KPIs | Ericsson |
| R3-242070 | (draft) Reply LS on improved KPIs | Ericsson |
| R3-242104 | Response to R3-241661 Considerations on NW based solution for DL non-SDT | Wuhan Hongxin Technology |
| R3-242105 | RedCap UE MBS Broadcast reception [RedcapMBS] | Huawei, CBN, Qualcomm Incorporated, ZTE, Nokia, Ericsson, Lenovo |
| R3-242106 | Correction on SDT RRC Release with resume indication [SDT_ReleaseEnh] | ZTE, Huawei, China Telecom, Qualcomm, LG Electronics, China Unicom, Samsung, CATT |
| R3-242107 | SDT RRC Release with resume indication [SDT_ReleaseEnh] | Huawei, Qualcomm Incorporated, Lenovo, ZTE, LG Electronics, Samsung |
| R3-242188 | Reply LS on SDT signalling optimization for partial context transfer | ZTE |
| R3-242198 | Reply LS on SDT signalling optimization for partial context transfer | RAN3(ZTE) |
| 9.1 | LTE | |
| R3-241523 | Reply LS on UE Location Information for NB-IoT NTN | SA2(Qualcomm) |
| R3-241609 | Support UE Location Information for NB-IoT NTN | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-241610 | Draft Response for LS on UE Location Information for NB-IoT NTN | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-241644 | Correction on RedCap UE inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone |
| R3-241645 | Correction on RedCap UE inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone |
| R3-241646 | Correction on eRedCap UE inter-system S1/NG-handover | Ericsson, Qualcomm Inc., China Telecom, Vodafone |
| R3-241761 | Discussion on UE Location Information for NB-IoT NTN with draft LS | CATT |
| R3-241907 | Discussion on UE Location Information for NB-IoT NTN | Huawei, Ericsson, Apple, Thales |
| R3-241922 | Discussion on UE Location Information for NB-IoT NTN | ZTE |
| R3-241996 | Support User Location Information reporting for NB-IoT NTN | Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-242023 | RAT type information | Vodafone GmbH |
| R3-242030 | Discussion on handover restriction of (e)RedCap | CATT, China Telecom |
| R3-242032 | [DRAFT] Reply LS on UE Location Information for NB-IoT NTN | Ericsson, Huawei, Apple, Thales |
| R3-242033 | E-SMLC OAM Configuration for IoT NTN | Ericsson, Thales, Huawei |
| 9.2.1 | 2RX for XR | |
| R3-241531 | Introduction of XR Broadcast Information IE for XnAP [2Rx_XR_Device] | ZTE, Qualcomm, China Telecom, Xiaomi, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Huawei, CATT |
| R3-241696 | Introduction of 2Rx XR support [2Rx_XR_Device] | Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, China Telecom, Xiaomi, Samsung, Ericsson, CMCC, Huawei, CATT |
| R3-241738 | Introduction of 2Rx XR support [2Rx_XR_Device] | Samsung, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, ZTE, CMCC, Huawei, Qualcomm, CATT, Xiaomi |
| R3-242007 | Clarification the usage of 2Rx indication for XR devices | CATT, Nokia, Nokia Shanghai Bell, CMCC |
| R3-242078 | Support of 2Rx XR UE inter system S1/NG-handover [2Rx_XR_Device] | Ericsson LM |
| R3-242108 | Introduction of 2Rx XR support [2Rx_XR_Device] | Samsung, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, ZTE, CMCC, Huawei, Qualcomm, CATT, Xiaomi |
| 9.2.2 | Others | |
| R3-241508 | LS on bandwidth aggregation for positioning | RAN1(ZTE) |
| R3-241509 | LS on SCPAC inter node agreements | RAN2(Ericsson) |
| R3-241510 | Reply LS on coverage condition for Ranging/Sidelink Positioning | RAN2(ZTE) |
| R3-241511 | Reply LS on SL-PRS resource allocation | RAN2(Xiaomi) |
| R3-241512 | Questions on RAN1 parameter list | RAN2(CATT) |
| R3-241518 | Reply LS on UE RACH-less handover for mobile IAB | RAN2(ZTE) |
| R3-241519 | Updates on measurement report mapping for Positioning Enhancements WI | RAN4(Huawei) |
| R3-241521 | Reply LS on RAN3 agreements on mobile IAB | SA2(Huawei) |
| R3-241530 | Discussion on Remaining Issues for LTM | Nokia |
| R3-241533 | Support Cell DTX/DRX in split architecture | CATT, ZTE, NEC |
| R3-241534 | Conditional Handover Request for NES | CATT |
| R3-241535 | Correction for the criticality of BAP address IE | CATT, ZTE, Fujitsu, Samsung, Xiaomi |
| R3-241536 | Corrections on mobile IAB procedures | CATT, Huawei, Fujitsu |
| R3-241537 | IAB-node De-registration Handling | CATT, Ericsson, Huawei, ZTE |
| R3-241538 | IAB-node de-registration handling | CATT, Ericsson, Huawei, ZTE |
| R3-241539 | IAB-node de-registration handling | CATT, Ericsson, Huawei, ZTE |
| R3-241548 | Support Cell DTXDRX in split architecture | CATT, ZTE, NEC |
| R3-241550 | Correction for RAN TSS reporting for multiple TSCTSF | Nokia, Ericsson, Huawei, Qualcomm Incorporated, ZTE |
| R3-241557 | Clarification of the bearer menagement in case of CHO with SCG | Nokia |
| R3-241558 | Triggering of the DL LBT reporting in case of multiple target nodes (incl. draft CRs to TS 38.300, TS 38.423 and TS 38.473) | Nokia |
| R3-241563 | (CR to 38.413) Correct the description of the selected PLMN indication in INITIAL UE MESSAGE | China Telecom, Huawei, CATT |
| R3-241564 | (CR to 38.413) Correct the description of the selected PLMN indication in INITIAL UE MESSAGE | China Telecom, Huawei, CATT |
| R3-241578 | Correction for 38.413 Reference specification | NEC, CMCC, NTT DOCOMO |
| R3-241579 | Correction for 38.413 Reference specification | NEC, CMCC, NTT DOCOMO |
| R3-241580 | Correction for early sync of LTM | NEC, Google Inc., LG Electronics, ZTE, Huawei, Samsung |
| R3-241586 | Introduction of SL related information transmission over F1 interface | NEC, ZTE, Samsung, CMCC |
| R3-241587 | Introduction of SL related information transmission over F1 interface | NEC, ZTE, Samsung, CMCC |
| R3-241588 | Corrections for SL Relay N3C related description | NEC |
| R3-241595 | SSB Beam deactivation for NES | NEC |
| R3-241599 | OAM requirements for the AI/ML for NG-RAN stage 2 | NEC, Huawei |
| R3-241600 | Corrections on AI/ML for NG-RAN stage 2 | NEC, Nokia, Lenovo, CATT, ZTE, Samsung |
| R3-241602 | Information of RedCap NCD-SSB over Xn interface | NEC |
| R3-241608 | (e)RedCap Rx branches indication over F1 Paging | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-241626 | IAB-node De-registration Handling | Ericsson, Huawei, CATT, ZTE |
| R3-241627 | IAB-node De-registration Handling | Ericsson, Huawei, CATT, ZTE |
| R3-241628 | IAB-node De-registration Handling | Ericsson, Huawei, CATT, ZTE |
| R3-241639 | Introduction of Measurement Quality and Time Stamp Information to E-CID | Ericsson, Comtech, Verizon Wireless, Polaris Wireless, Nokia |
| R3-241640 | Introduction of Measurement Quality and Time Stamp Information to E-CID | Ericsson, Comtech, Verizon Wireless, Polaris Wireless, Nokia |
| R3-241641 | Introduction of Measurement Quality and Time Stamp Information to E-CID | Ericsson, Comtech, Verizon Wireless, Polaris Wireless, Nokia |
| R3-241642 | Support of pre-Configured SRS activation using full context relocation | Ericsson, Xiaomi, Nokia, Qualcomm Incorporated |
| R3-241643 | Correction of MT Communication Handling procedure | Ericsson, Huawei, Nokia, Xiaomi, Qualcomm Inc., ZTE, CATT |
| R3-241649 | Support MUSIM capability restriction over XnAP | Ericsson, Qualcomm, Xiaomi |
| R3-241650 | Support MUSIM capability restriction over XnAP | Ericsson, Qualcomm Incorporated, Xiaomi |
| R3-241652 | Correction of handling GTP-U Error Indication | Ericsson, Nokia, Huawei |
| R3-241653 | Support MUSIM capability restriction | Ericsson, Qualcomm, Xiaomi |
| R3-241654 | Support MUSIM capability restriction over NGAP | Ericsson, Qualcomm Incorporated, Xiaomi |
| R3-241655 | Correction on musim-CapabilityRestrictionIndication IE | Ericsson, Qualcomm Incorporated, Xiaomi |
| R3-241658 | Support of the pre-Configured SRS activation | Xiaomi, Ericsson, Nokia, Qualcomm Incorporated |
| R3-241665 | Correction of handling GTP-U Error Indication | Nokia, Ericsson, Huawei |
| R3-241666 | Correction of handling GTP-U Error Indication | Huawei, Nokia, Ericsson |
| R3-241667 | Correction on the MT communication handling procedure | Huawei, ZTE, Ericsson, Nokia, CATT, Qualcomm Incorporated, China Telecom |
| R3-241674 | Correction on BC session path update for network sharing | Huawei, CBN, Nokia, Qualcomm Incorporated, Samsung, CATT |
| R3-241675 | Correction on MBS UP failure_option 1 | Huawei, CBN, Nokia, Qualcomm Incorporated |
| R3-241676 | Correction on source MRB progress | Huawei, CBN, Nokia, Qualcomm Incorporated, Samsung |
| R3-241677 | Correction on source MRB progress | Huawei, CBN, Nokia, Qualcomm Incorporated, Samsung |
| R3-241678 | Correction on indirect data forwarding [Indirect Data forwarding] | Huawei, Nokia, Samsung, LG Electronics, ZTE |
| R3-241687 | Correction of Time Reference Information | Huawei, Nokia, ZTE, Ericsson, Deutsche Telekom |
| R3-241688 | Correction of Time Reference Information | Huawei, Nokia, ZTE, Ericsson, Deutsche Telekom |
| R3-241689 | Correction of Time Reference Information | Huawei, Nokia, ZTE, Ericsson, Deutsche Telekom |
| R3-241690 | Correction of QoS Flow List | Huawei, Deutsche Telekom, CATT |
| R3-241691 | Correction of QoS Flow List | Huawei, Deutsche Telekom, CATT |
| R3-241692 | Correction of QoS Flow List | Huawei, Deutsche Telekom, CATT |
| R3-241695 | UL SDT for MT communication handling | ZTE, Qualcomm, CATT, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Xiaomi |
| R3-241697 | Introduction of MDBV in the Alternative QoS | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm |
| R3-241698 | Introduction of MDBV in the Alternative QoS | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm |
| R3-241699 | Clarification on non-homogeneous deployment | Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT |
| R3-241700 | Correction on MT Communication Handling Procedures in TS 38.410 | China Telecom, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-241701 | Correction on the missing SIB18 in TS 38.473 | China Telecom,ZTE,CATT |
| R3-241702 | Correction on the missing SIB18 in TS 38.473 | China Telecom, ZTE, CATT |
| R3-241703 | Correction on the missing SIB19 in TS 38.473 | China Telecom, ZTE, CATT |
| R3-241704 | Correction on the missing SIB19 in TS 38.473 | China Telecom, ZTE, CATT |
| R3-241705 | Missing procedure description for pre-configured SRS activation | Qualcomm Incorporated, Ericsson, Nokia, Xiaomi |
| R3-241706 | Correction on IAB-node de-registration handling | Huawei, Ericsson, CATT, ZTE |
| R3-241707 | Correction on IAB-node de-registration handling | Huawei, Ericsson, CATT, ZTE |
| R3-241708 | Correction on IAB-node de-registration handling | Huawei, Ericsson, CATT, ZTE |
| R3-241709 | Correction on IAB-node de-registration handling | Huawei, Ericsson, CATT, ZTE |
| R3-241710 | Correction on IAB-node de-registration handling | Huawei, Ericsson, CATT, ZTE |
| R3-241711 | Correction on mobility support for mobile IAB without PDU session | Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Lenovo, Samsung |
| R3-241712 | Discussion on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm |
| R3-241713 | Correction on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Xiaomi, Qualcomm |
| R3-241714 | Correction on DL PSI based discard | Huawei, Ericsson, Lenovo, CMCC, Qualcomm |
| R3-241722 | LTM corrections to F1AP | Huawei, China Telecom, CATT |
| R3-241727 | Discussion on LTM remaining issues (CR included) | Huawei |
| R3-241739 | Discussion on non-integer DRX cycle issue for XR | Samsung, Xiaomi, Cybercore |
| R3-241740 | Correction to TS 38.473 on non-integer DRX cycle issue for XR | Samsung, Xiaomi, Cybercore |
| R3-241753 | Discussion on Efficient PDU Discard in CU-DU Split Architecture | Xiaomi |
| R3-241754 | Support of discard coordination between CU and DU | Xiaomi |
| R3-241755 | Support of discard coordination between CU and DU | Xiaomi |
| R3-241756 | Correction on candidate gNB DU ID list and TCI state index | CATT, Huawei, China Telecom, CMCC, ZTE, Nokia, Nokia Shanghai Bell, NEC, Ericsson, Lenovo, Rakuten,Samsung |
| R3-241757 | Correction on the LTM configuration ID and LTM configuration ID Mapping list | CATT, China Telecom, Nokia, Nokia Shanghai Bell, Samsung, Google, CMCC, ZTE, Huawei, Ericsson |
| R3-241762 | Correction of IP-Sec Transport Layer Address | Huawei, China Telecom, China Unicom, Ericsson |
| R3-241763 | Correction of IP-Sec Transport Layer Address | Huawei, China Telecom, China Unicom, Ericsson |
| R3-241764 | Correction of IP-Sec Transport Layer Address | Huawei, China Telecom, China Unicom, Ericsson |
| R3-241765 | Effective measurement window for inter-RAT measurement | Huawei, China Telecom, China Unicom, Nokia |
| R3-241766 | Correction on textual description of Early Status Transfer procedure | ZTE, CMCC, China Unicom |
| R3-241767 | Correction on textual description of Early Status Transfer procedure | ZTE, CMCC, China Unicom |
| R3-241768 | Correction on textual description of Early Status Transfer procedure | ZTE, CMCC, China Unicom |
| R3-241771 | Resolution of User Plane Failure scenarios | Nokia, Huawei, Qualcomm Incorporated |
| R3-241772 | Correction of F1-U failure recovery - option 1 | Nokia, Huawei, Qualcomm Incorporated |
| R3-241773 | Correction of F1-U failure recovery - option 3 | Nokia, Huawei, Qualcomm Incorporated |
| R3-241774 | Correction of F1-U failure recovery - option 3 | Nokia, Huawei, Qualcomm Incorporated |
| R3-241775 | Correction of MBS non-shared gNB-DU | Nokia, Huawei, Qualcomm Incorporated |
| R3-241776 | Correction of MBS non shared DU | Nokia, Huawei, Qualcomm Incorporated |
| R3-241777 | Correction of Data Forwarding Handling of MRB | Nokia, Huawei, Qualcomm Incorporated |
| R3-241778 | Correction of Data forwarding handling of MRB | Nokia, Huawei, Qualcomm Incorporated |
| R3-241779 | Correction of Data Forwarding Handling of MRB | Nokia, Huawei, Qualcomm Incorporated |
| R3-241780 | Correction of Slice Availability | Nokia, Deutsche Telekom |
| R3-241782 | Correction on LTM | Lenovo |
| R3-241783 | Correction on LTM | Lenovo |
| R3-241784 | Correction on burst arrival time in handover | Lenovo |
| R3-241785 | Correction on End PDU Indication in Data Forwarding | Lenovo |
| R3-241786 | Correction on inter MN handover without SN change for QMC | Lenovo, Huawei |
| R3-241815 | Resolving remaining issues for Intra-CU LTM | Ericsson |
| R3-241816 | Further corrections on LTM in stage-2 | Ericsson |
| R3-241817 | Further corrections on LTM over F1 | Ericsson |
| R3-241818 | Corrections on preamble index allocation | Ericsson, ZTE, Lenovo |
| R3-241828 | Discussion on handling of GTP-U exception and User plane failure | CATT |
| R3-241857 | Corrections for LTM for reconfiguration with sync | Google, Inc. |
| R3-241860 | Correction on mobile IAB-MT migration | Huawei, CATT, Nokia, Nokia Shanghai Bell |
| R3-241861 | Correction on MDBV for alternative QoS | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-241862 | Correction on MDBV for alternative QoS | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-241863 | Correction on DL PSI based discard | Huawei, CATT, CMCC, Qualcomm |
| R3-241864 | Correction on non-integer DRX cycle | Huawei, Lenovo, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-241873 | IAB-node De-registration Handling | ZTE, Ericsson, Huawei, CATT |
| R3-241874 | IAB-node De-registration Handling | ZTE, Ericsson, Huawei, CATT |
| R3-241875 | IAB-node De-registration Handling | ZTE, Ericsson, Huawei, CATT |
| R3-241876 | Support of no PDU session for IAB-MT during Path Switch Request procedure | ZTE, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei, Lenovo, Samsung |
| R3-241877 | Support of no PDU session for IAB-MT during Path Switch Request procedure | ZTE, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei, Lenovo, Samsung |
| R3-241878 | Correction on missing IE for sidelink DRX reference-option1 | ZTE Corporation, Sanechips, China Telecom, Samsung |
| R3-241879 | Correction on missing IE for sidelink DRX reference-option2 | ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell, CMCC, CATT |
| R3-241880 | Correction on missing IE for sidelink DRX reference-option2 | ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell, CMCC |
| R3-241881 | Correction on text description of UE trajectory information | ZTE, CATT, Samsung, China Unicom, Lenovo, NEC |
| R3-241882 | Correction on missing procedure for positioning | ZTE, CATT, Ericsson, Huawei, Xiaomi, Nokia |
| R3-241883 | Correction on measurement report for SRS Bandwidth Aggregation | ZTE, CATT, Ericsson |
| R3-241884 | Correction on SRS Bandwidth Aggregation Configuration | ZTE, China Unicom, China Telecom |
| R3-241885 | Correction on SRS Bandwidth Aggregation Configuration | ZTE, China Unicom, China Telecom |
| R3-241886 | Correction on Inter-system MRO | ZTE, Samsung, CMCC, Nokia |
| R3-241887 | Correction on Inter-system MRO | ZTE, Samsung, CMCC, Nokia |
| R3-241888 | (CR to 38.401) Corrections on LTM procedures | China Telecom, Huawei, CATT, Nokia, Google |
| R3-241904 | Correction to 38.473 on NES CHO awareness at source gNB-DU | Qualcomm Incorporated |
| R3-241906 | Various corrections on Rel-18 Positioning | Huawei |
| R3-241911 | Addition of SON for fast MCG recovery in stage 2 | Samsung, Lenovo, CATT, Nokia, ZTE |
| R3-241912 | Issue on inter-system MRO | Samsung, ZTE, Nokia, CMCC |
| R3-241913 | Correction on Inter-system MRO | Samsung, ZTE, Nokia, CMCC |
| R3-241914 | Correction on Inter-system MRO | Samsung, Nokia, ZTE, CMCC |
| R3-241915 | Addition of CPAC detection in stage 2 | Samsung, Lenovo, CATT, Cybercore |
| R3-241917 | Correction on Handover Cancel in CHO with SN | Samsung |
| R3-241918 | Correction on configuration modification and release in CHO with candidate SCGs | Samsung |
| R3-241919 | Correction on the missing SIB18 in TS 38.473 | China Telecom, ZTE,CATT |
| R3-241920 | Correction on the missing SIB19 in TS 38.473 | China Telecom, ZTE,CATT |
| R3-241923 | CR to 38.401 on procedures of enabling multicast reception in RRC_INACTIVE | ZTE, CBN, Huawei, Samsung, Lenovo, CATT, Qualcomm Incorporated |
| R3-241928 | Correction on measurement report for SRS Bandwidth Aggregation | CATT, ZTE, Ericsson |
| R3-241929 | Discussion on pre-configured SRS activation | CATT |
| R3-241948 | Correction on Data Collection procedures over Xn | CMCC, ZTE, CATT, Huawei |
| R3-241953 | Correction on user consent for trace reporting | CMCC, Huawei |
| R3-241954 | Correction on inter-system MRO | CMCC, Samsung, ZTE, Nokia |
| R3-241969 | Discussion on direct data forwarding in SCPAC | Samsung, CATT, Huawei, ZTE, Cybercore |
| R3-241970 | Correction on direct data forwarding in SCPAC | Samsung, CATT, Huawei, Cybercore |
| R3-241971 | Stage2 correction on direct data forwarding | Samsung, CATT, Huawei, Cybercore |
| R3-241972 | Correction on Inter-system MRO for TS36.300_R17 | Nokia |
| R3-241973 | Correction to DL-PRS Aggregation | Qualcomm Incorporated |
| R3-241974 | Correction on Inter-system MRO | Nokia, ZTE, Samsung, CMCC |
| R3-241975 | Corrections on SL relay procedure | LG Electronics |
| R3-241976 | Corrections on SL relay | LG Electronics |
| R3-241977 | Correction on measurement report for SRS Bandwidth Aggregation | ZTE, CATT, Ericsson |
| R3-241978 | Correction on configuration of SRS Bandwidth Aggregation | ZTE, China Unicom, China Telecom |
| R3-241982 | Stage 3 corrections for UAV | Huawei |
| R3-241983 | Stage 2 corrections for AI/ML for NG-RAN | Huawei, Deutsche Telekom, CMCC, Telecom Italia, Nokia |
| R3-241984 | Stage 2 corrections for AI/ML for NG-RAN | Huawei, Deutsche Telekom, CMCC, Telecom Italia, Nokia |
| R3-241985 | Stage 3 corrections for AI/ML for NG-RAN | Huawei, Nokia, Qualcomm Incorporated, InterDigital |
| R3-241992 | Discussion on LTM remaining issues | ZTE |
| R3-241993 | Correction on inter-system MRO | CMCC, Samsung, ZTE, Nokia |
| R3-241994 | Discussion on issues related to RAN2 decisions for LTM | Samsung,CATT, Lenovo |
| R3-241995 | Discussion on Remaining issues for LTM | Samsung |
| R3-242005 | Correction to 38.473 for non-integer DRX in XR | CATT, Ericsson |
| R3-242006 | Correction to 38.423 for SON features enhancement | CATT, Samsung, ZTE |
| R3-242014 | Discussion on peer UE ID for U2U relay | ZTE, Samsung, China Telecom, NEC, Sanechips |
| R3-242015 | Corrections on PC5 RLC channel configuration for U2U relay | ZTE, Samsung, China Telecom, NEC, Sanechips |
| R3-242016 | Correction on receipt of GTP-U Error Indication | ZTE |
| R3-242017 | Correction on receipt of GTP-U Error Indication | ZTE |
| R3-242018 | Correction on stage 2 of PSCell List of RA report | ZTE, CATT, China Telecom |
| R3-242019 | Correction on PSCell List Container List of RA report | ZTE, CATT, China Telecom |
| R3-242020 | Correction on PSCell List Container List of RA report | ZTE, CATT, China Telecom |
| R3-242029 | Stage 2 correction for NR-U | Ericsson, Huawei, Qualcomm Incorporated |
| R3-242031 | QoE measurement handling in RRC_IDLE and RRC_INACTIVE states | CATT, Ericsson, ZTE, Xiaomi |
| R3-242034 | Discussion on corrections to QMC support in NR-DC | Samsung |
| R3-242035 | Corrections to QMC support in NR-DC | Samsung |
| R3-242046 | Correcting criticality for mobility change procedure | Huawei |
| R3-242047 | Correcting criticality for mobility change procedure | Huawei |
| R3-242048 | Correcting criticality for mobility change procedure | Huawei |
| R3-242049 | Correcting IE referenced in Coverage Modification | Huawei |
| R3-242050 | Correcting IE referenced in Coverage Modification | Huawei |
| R3-242051 | Discussion on the Security Key IE for non-3GPP access | Nokia, Nokia Shanghai Bell |
| R3-242054 | Correction on NGAP to support the QoE mobility during NG-based inter-MN HO | ZTE, China Unicom, China Telecom, CMCC, Samsung, CATT |
| R3-242055 | Inter-node cell DTX/DRX configuration exchange for NES | ZTE, China Unicom |
| R3-242058 | (e)RedCap Rx branches indication over F1 Paging | Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-242059 | Correction on the QMC information in the SN modification required message | Huawei, China Unicom, Ericsson, Lenovo |
| R3-242060 | Further miscellaneous corrections to 38.300 | Huawei, China Unicom, Lenovo |
| R3-242061 | Further miscellaneous corrections to 37.340 | Huawei, China Unicom, Lenovo |
| R3-242064 | SN-initiated flag signalling for SPR | Ericsson |
| R3-242071 | Clarifications on Effective Measurement Window | Ericsson |
| R3-242079 | Corrections for DU-CU/CU-DU Cell Switch notification message | ZTE |
| R3-242081 | Correction on the missing SIB20 in TS 38.470 | ZTE, China Telecom, China Unicom |
| R3-242082 | Correction on the missing SIB20 in TS 38.470 | ZTE, China Telecom, China Unicom |
| R3-242083 | Correction on the missing SIB9 in TS 38.470 | ZTE, China Telecom, China Unicom |
| R3-242084 | Correction on the missing SIB9 in TS 38.470 | ZTE, China Telecom, China Unicom |
| R3-242085 | Correction on the missing SIB9 in TS 38.470 | ZTE, China Telecom, China Unicom |
| R3-242086 | Correction on indirect Data forwarding | ZTE, LG Electronics, China Telecommunication, Huawei, Samsung |
| R3-242091 | Correction on Rel-18 indirect data forwarding indication [Indirect Data Forwarding] | LG Electronics Inc. |
| R3-242092 | Rel-18 LTM UE based TA measurement configuration to DU | LG Electronics Inc. |
| R3-242093 | Rel-18 LTM correction for UE-based TA measurement configuration from CU to DU | LG Electronics Inc. |
| R3-242094 | Rel-18 LTM correction for UE-based TA measurement configuration from CU to DU | LG Electronics Inc. |
| R3-242095 | Rel-18 LTM correction for LTM with gNB-CU-UP change | LG Electronics Inc. |
| R3-242109 | CB#2_GTP-Uerror | Nokia |
| R3-242110 | CB:#3_Positioning | CATT |
| R3-242111 | IAB-node de-registration handling | CATT, Ericsson, Huawei, ZTE |
| R3-242112 | IAB-node De-registration Handling | Ericsson, Huawei, CATT, ZTE |
| R3-242113 | Correction on IAB-node de-registration handling | Huawei, Ericsson, CATT, ZTE |
| R3-242114 | Correction on IAB-node de-registration handling | Huawei, Ericsson, CATT, ZTE |
| R3-242115 | IAB-node De-registration Handling | ZTE, Ericsson, Huawei, CATT |
| R3-242116 | Support of no PDU session for IAB-MT during Path Switch Request procedure | ZTE, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei, Lenovo, Samsung |
| R3-242117 | Support of no PDU session for IAB-MT during Path Switch Request procedure | ZTE, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei, Lenovo, Samsung |
| R3-242118 | Correction on mobility support for mobile IAB without PDU session | Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Lenovo, Samsung |
| R3-242119 | Corrections on mobile IAB procedures | CATT, Huawei, Fujitsu, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Ericsson |
| R3-242120 | Correction on mobile IAB-MT migration | Huawei, CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-242121 | Clarification of the bearer menagement in case of CHO with SCG | Nokia, LG Electronics |
| R3-242122 | CB:#5_SPAC | Samsung |
| R3-242123 | Correction on candidate gNB DU ID list and TCI state index | CATT, Huawei, China Telecom, CMCC, ZTE, Nokia, Nokia Shanghai Bell, NEC, Ericsson, Lenovo, Rakuten,Samsung |
| R3-242124 | Correction for early sync and TCI state of LTM | NEC, Google Inc., LG Electronics, ZTE, Huawei, Samsung, CATT, China Telecom, CMCC, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, Rakuten |
| R3-242125 | Correction on the LTM configuration ID and LTM configuration ID Mapping list | CATT, China Telecom, Nokia, Nokia Shanghai Bell, Samsung, Google, CMCC, ZTE, Huawei, Ericsson, NEC, LG Electronics |
| R3-242126 | CB:#6_LTM | Huawei |
| R3-242127 | Introduction of MDBV in the Alternative QoS | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm, ZTE, China Telecom, Ericsson, CMCC, Xiaomi, Samsung, Lenovo, CATT |
| R3-242128 | Introduction of MDBV in the Alternative QoS | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm, ZTE, China Telecom, Ericsson, CMCC, Xiaomi, Samsung, Lenovo, CATT |
| R3-242129 | Correction on MDBV for alternative QoS | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, China Telecom, Ericsson, Samsung, Xiaomi, CMCC, Lenovo, CATT |
| R3-242130 | Correction on MDBV for alternative QoS | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, China Telecom, Ericsson, Samsung, Xiaomi, CMCC, Lenovo, CATT |
| R3-242131 | Clarification on non-homogeneous deployment | Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT, Ericsson, Qualcomm Inc, CMCC, Xiaomi, Samsung, Lenovo, CATT |
| R3-242132 | Correction on DL PSI based discard | Huawei, CATT, CMCC, Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, China Telecom |
| R3-242133 | (Void) Canceled allocation | MCC |
| R3-242134 | Correction on non-integer DRX cycle | Huawei, Lenovo, China Telecom, Nokia, Nokia Shanghai Bell, ZTE, CATT, Ericsson, Qualcomm, LG Electronics Inc., Samsung, CMCC |
| R3-242135 | Correction of MT Communication Handling procedure | Ericsson, Huawei, Nokia, Xiaomi, Qualcomm Inc., ZTE, CATT |
| R3-242136 | UL SDT for MT communication handling | ZTE, Qualcomm, CATT, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Xiaomi |
| R3-242137 | Correction on MT Communication Handling Procedures in TS 38.410 | China Telecom, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-242138 | Correction on missing IE for sidelink DRX reference-option1 | ZTE Corporation, Sanechips, China Telecom, Samsung, Nokia, Nokia Shanghai Bell, LG Electronics Inc., Ericsson |
| R3-242139 | Introduction of SL related information transmission over F1 interface | NEC, ZTE, Samsung, CMCC |
| R3-242140 | Introduction of SL related information transmission over F1 interface | NEC, ZTE, Samsung, CMCC |
| R3-242155 | Corrections for SL Relay N3C related description | NEC |
| R3-242162 | Correction on measurement report for SRS Bandwidth Aggregation | ZTE, CATT, Ericsson, Huawei, Nokia, Samsung, Xiaomi |
| R3-242163 | Correction on measurement report for SRS Bandwidth Aggregation | CATT, ZTE, Ericsson, Huawei |
| R3-242168 | Correction on the missing SIB18 in TS 38.473 | China Telecom, ZTE,CATT |
| R3-242169 | Correction on the missing SIB18 in TS 38.473 | China Telecom, ZTE, CATT |
| R3-242170 | Correction on the missing SIB19 in TS 38.473 | China Telecom, ZTE,CATT |
| R3-242171 | Correction on the missing SIB19 in TS 38.473 | China Telecom, ZTE, CATT |
| R3-242173 | Corrections for LTM for reconfiguration with sync | Google, Inc. |
| R3-242174 | Various corrections on Rel-18 Positioning | Huawei, CATT, Ericsson, Nokia, Xiaomi, Samsung, ZTE |
| R3-242175 | Various corrections on Rel-18 Positioning | Huawei, CATT, Ericsson, Nokia, Xiaomi, Samsung, ZTE |
| R3-242176 | Correction on user consent for trace reporting | CMCC, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-242177 | LTM corrections to F1AP | Huawei, China Telecom, CATT, Google, Inc., Ericsson, Nokia, LG Electronics |
| R3-242178 | Correction on text description of UE trajectory information | ZTE, CATT, Samsung, China Unicom, Lenovo, NEC, Ericsson, Nokia |
| R3-242179 | Corrections on SL relay | LG Electronics, Nokia, Nokia Shanghai Bell, Samsung |
| R3-242180 | OAM requirements for the AI/ML for NG-RAN stage 2 | NEC, Huawei |
| R3-242181 | Corrections on PC5 RLC channel configuration for U2U relay | ZTE, Samsung, China Telecom, NEC, Sanechips, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-242182 | Stage2 correction on direct data forwarding | Samsung, CATT, Huawei, Cybercore |
| R3-242183 | Correction of handling GTP-U Error Indication | Nokia, Ericsson, Huawei, ZTE |
| R3-242184 | Correction of handling GTP-U Error Indication | Huawei, Nokia, Ericsson, ZTE |
| R3-242185 | Introduction of Measurement Quality and Time Stamp Information to E-CID [ECIDQualTimeStamp] | Ericsson, Comtech, Verizon Wireless, Polaris Wireless, Nokia, ZTE |
| R3-242186 | Introduction of Measurement Quality and Time Stamp Information to E-CID [ECIDQualTimeStamp] | Ericsson, Comtech, Verizon Wireless, Polaris Wireless, Nokia, ZTE |
| R3-242187 | Introduction of Measurement Quality and Time Stamp Information to E-CID [ECIDQualTimeStamp] | Ericsson, Comtech, Verizon Wireless, Polaris Wireless, Nokia, ZTE |
| R3-242189 | Correction on musim-CapabilityRestrictionIndication IE | Ericsson, Qualcomm Incorporated, Xiaomi |
| R3-242190 | (Cancelled allocation) | MCC |
| R3-242191 | Corrections for DU-CU/CU-DU Cell Switch notification message | ZTE, Nokia, Ericsson, Huawei, CATT, China Telecom, LG Electronics |
| R3-242193 | (CR to 38.401) Corrections on LTM procedures | China Telecom, Huawei, CATT, Nokia, Nokia Shanghai Bell, Google, ZTE, Ericsson |
| R3-242194 | Correction on burst arrival time in handover | Lenovo, Huawei, CATT, CMCC, ZTE, Xiaomi, Samsung, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-242196 | Further corrections on LTM in stage-2 | Ericsson |
| R3-242197 | Further corrections on LTM over F1 | Ericsson |
| R3-242199 | Rel-18 LTM correction for LTM with gNB-CU-UP change | LG Electronics, Google, Ericsson, Nokia, Huawei,CATT, Lenovo |
| R3-242200 | Clarification of the bearer menagement in case of CHO with SCG | Nokia, LG Electronics |
| R3-242201 | Stage2 correction on direct data forwarding | Samsung, CATT, Huawei, Cybercore, ZTE, Nokia, LG Electronics, Ericsson |
| R3-242203 | Corrections for SL Relay N3C related description | NEC, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-242204 | Correction for early sync and TCI state of LTM | NEC, Google Inc., LG Electronics, ZTE, Huawei, Samsung, CATT, China Telecom, CMCC, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, Rakuten |
| R3-242205 | Stage 2 corrections for AI/ML for NG-RAN | Huawei, Deutsche Telekom, CMCC, Telecom Italia, Nokia |
| R3-242206 | Stage 3 corrections for AI/ML for NG-RAN | Huawei, Nokia, Qualcomm Incorporated, InterDigital |
| R3-242207 | Corrections on LTM procedures | China Telecom, Huawei, CATT, Nokia, Nokia Shanghai Bell, Google, ZTE, Ericsson, LG Electronics, NEC, CMCC |
| R3-242208 | LTM corrections to F1AP | Huawei, China Telecom, CATT, Google, Inc., Ericsson, Nokia, LG Electronics, ZTE, Lenovo |
| R3-242209 | Further corrections on LTM in stage-2 | Ericsson, Nokia, Lenovo, ZTE, Google Inc., LG Electronics Inc., CATT |
| R3-242210 | Corrections for SL Relay N3C related description | NEC, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-242211 | Further corrections on LTM over F1 | Ericsson, CATT, Huawei, Nokia, LG Electronics, Lenovo, ZTE |
| R3-242212 | Corrections for LTM for reconfiguration with sync | Google, Inc, CATT, Nokia, Ericsson, LG Electronics, Huawei, China Telecom, NEC, Lenovo, ZTE, CMCC |
| R3-242213 | Rel-18 LTM correction for LTM with gNB-CU-UP change | LG Electronics, Google, Ericsson, Nokia, Huawei, CATT, Lenovo, ZTE, CMCC, NEC, China Telecom, Samsung |
| R3-242214 | Corrections for DU-CU/CU-DU Cell Switch notification message | ZTE, Nokia, Ericsson, Huawei, CATT, China Telecom, LG Electronics, Lenovo |
| R3-242215 | Corrections on AI/ML for NG-RAN stage 2 | NEC, Nokia, Lenovo, CATT, ZTE, Samsung, Qualcomm, Huawei, Deutsche Telekom, CMCC, Telecom Italia |
| R3-242216 | Correction on non-integer DRX cycle | Huawei, Lenovo, China Telecom, Nokia, Nokia Shanghai Bell, ZTE, CATT, Ericsson, Qualcomm, LG Electronics Inc., Samsung, CMCC |
| R3-242217 | Various corrections on Rel-18 Positioning | Huawei, CATT, Ericsson, Nokia, Xiaomi, Samsung, ZTE |
| R3-242218 | Various corrections on Rel-18 Positioning | Huawei, CATT, Ericsson, Nokia, Xiaomi, Samsung, ZTE |
| R3-242219 | Addition of missing positioning SIBs | Nokia, CATT, Ericsson, Huawei, Qualcomm Incorporated, Samsung, Xiaomi, ZTE |
| R3-242220 | Addition of missing positioning SIBs | Huawei, Nokia, CATT, Ericsson, Qualcomm Incorporated, Samsung, Xiaomi, ZTE |
| R3-242221 | Corrections for SL Relay N3C related description | NEC, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-242222 | Corrections on SL relay | LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-242223 | Corrections on PC5 RLC channel configuration for U2U relay | ZTE, Samsung, China Telecom, NEC, Sanechips, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-242224 | Correction on measurement report for SRS Bandwidth Aggregation | CATT, ZTE, Ericsson, Huawei, Nokia, Samsung, Xiaomi |
| R3-242225 | Various corrections on Rel-18 Positioning | Huawei, CATT, Ericsson, Nokia, Xiaomi, Samsung, ZTE |
| R3-242226 | Various corrections on Rel-18 Positioning | Huawei, CATT, Ericsson, Nokia, Xiaomi, Samsung, ZTE |
| R3-242227 | Addition of missing positioning SIBs | Huawei, Nokia, CATT, Ericsson, Qualcomm Incorporated, Samsung, Xiaomi, ZTE |
| R3-242230 | Addition of missing positioning SIBs | Huawei, Nokia, CATT, Ericsson, Qualcomm Incorporated, Samsung, Xiaomi, ZTE |
| R3-242235 | Stage 3 corrections for AI/ML for NG-RAN | Huawei, Nokia, Qualcomm Incorporated, InterDigital, NEC, ZTE, CMCC, Ericsson, CATT |
| 9.3 | R18 Rapporteur Corrections | |
| R3-241551 | Remove a potential disprepancy between assigned IANA and F1AP layer 2 assigned values | InterDigital |
| R3-241574 | Rapporteur Corrections | Huawei |
| R3-241575 | Rapporteur Corrections | Huawei |
| R3-241618 | Correction on S1AP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| R3-241619 | Correction on X2AP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| R3-241620 | Correction on NGAP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| R3-241621 | Correction on XnAP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| R3-241630 | Correcting ASN.1 comments for conditional present IE | Ericsson |
| R3-241631 | Correcting ASN.1 comments for conditional present IE | Ericsson |
| R3-241632 | Correcting ASN.1 comments for conditional present IE | Ericsson |
| R3-241633 | Correcting ASN.1 comments for conditional present IEs | Ericsson |
| R3-241634 | Correcting ASN.1 comments for conditional present IE | Ericsson |
| R3-242062 | Rapporteur corrections to 37.482 | Huawei |
| R3-242141 | Correction on S1AP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| R3-242142 | Correction on F1AP PPID and Destination Port Number over SCTP | InterDigital |
| R3-242143 | Correction on X2AP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| R3-242144 | Correction on NGAP PPID and Destination Port Number over SCTP | NTTDOCOMO, INC. |
| 10.1 | General | |
| R3-241962 | Workplan for Rel-19 SON_MDT Enhancement | China Unicom, CMCC |
| R3-242150 | Workplan for Rel-19 SON_MDT Enhancement | China Unicom, CMCC |
| 10.2 | MRO Enhancements | |
| R3-241561 | Optimal usage of Subsequent CPAC | Nokia |
| R3-241571 | MRO enhancement for R18 mobility mechanisms | Huawei |
| R3-241585 | Discussion on MRO enhancement for Rel-18 mobility features | NEC |
| R3-241604 | MRO for LTM and CHO with Candidate SCG(s) | Nokia |
| R3-241605 | Discussion on LTM MRO enhancement | Fujitsu |
| R3-241728 | Discussion on MRO for LTM | Samsung |
| R3-241787 | Discussion on MRO for LTM and subsequent CPAC | Lenovo |
| R3-241788 | Discussion on MRO for CHO with candidate SCGs | Lenovo |
| R3-241853 | MRO enhancements for R18 mobility mechanisms | Qualcomm Incorporated |
| R3-241858 | Discussion on MRO enhancement for LTM | LG Electronics Inc. |
| R3-241910 | Discussion on MRO for CHO with candidate SCGs and S-CPAC | Samsung |
| R3-241955 | Discussion on MRO enhancements for R18 mobility features | CMCC |
| R3-241966 | Discussion on MRO Enhancements | China Unicom |
| R3-242008 | Discussion on SON enhancement for R18 mobility mechanisms | CATT |
| R3-242021 | Discussion on MRO | ZTE |
| R3-242024 | MRO enhancements for LTM | Ericsson |
| R3-242025 | Other MRO enhancements | Ericsson |
| 10.3.1 | Intra-NTN Mobility | |
| R3-241559 | Considerations on SON enhancements for NTN deployments | Nokia |
| R3-241723 | SON for Intra-NTN mobility | Huawei |
| R3-241737 | Discussion on SON enhancements for NTN | Samsung |
| R3-241769 | Initial Considerations on SON/MDT Enhancements for NTN | ZTE |
| R3-241789 | Discussion on SON enhancements for intra-NTN mobility | Lenovo |
| R3-241854 | SON MDT for NTN | Qualcomm Incorporated |
| R3-241939 | Discussion on SON/MDT enhancement for NTN | CMCC |
| R3-241967 | Discussion on SONMDT enhancements for NTN mobility | China Unicom |
| R3-242009 | Discussion on intra-NTN mobility for SONMDT | CATT |
| R3-242026 | SON/MDT enhancements for NTN | Ericsson |
| 10.3.2 | Network Slicing | |
| R3-241560 | Considerations on SON enhancements for Network Slicing | Nokia |
| R3-241572 | SON for Network Slicing | Huawei |
| R3-241855 | SON MDT for network slicing | Qualcomm Incorporated |
| R3-241945 | Discussion on SONMDT for network slicing | CMCC |
| R3-241968 | Discussion on SONMDT enhancements for network slicing | China Unicom |
| R3-242010 | Discussion on network slicing for SONMDT | CATT |
| R3-242022 | Initial consideration on SON/MDT for Slicing | ZTE |
| R3-242027 | Network slicing observability enhancements for SON/MDT | Ericsson |
| 10.4 | R18 leftovers | |
| R3-241573 | Rel-18 SON/MDT leftovers | Huawei |
| R3-241790 | (TP for SON BLCR for 36.300) Discussion on MRO for MR-DC SCG failure | Lenovo |
| R3-241916 | Discussion on the support of the leftovers in Rel-18 SON/MDT | Samsung |
| R3-241921 | Discussion on Rel-18 Leftover Issues | ZTE |
| R3-241940 | Discussion on SON/MDT Enhancements for SDT and MHI | CMCC |
| R3-242011 | Discussion on SON enhancement for R18 leftover | CATT |
| R3-242028 | SON discussion for SDT | Ericsson, Deutsche Telekom, AT&T |
| R3-242195 | LS on support of MRO for MR-DC SCG failure | RAN3(ZTE) |
| 11.1 | General | |
| R3-241865 | Skeleton for TR38.743 v0.0.0 | ZTE |
| R3-241866 | Work plan for Study on enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN | ZTE, NEC |
| R3-242243 | Skeleton for TR38.743 v0.0.0 | ZTE |
| 11.2 | AI/ML enabled Slicing | |
| R3-241589 | Considerations on AI/ML based network slicing | NEC |
| R3-241590 | TP to TR38.743 for AI/ML-based Network Slicing | NEC |
| R3-241611 | Discussion on NG-RAN AI/ML for Network Slicing | Qualcomm Incorporated |
| R3-241729 | (TP to TR 38.743) AI/ML enabled slicing | Samsung |
| R3-241791 | Discussion on AIML based network slicing | Lenovo |
| R3-241792 | TP to 38.743 for AIML based network slicing | Lenovo |
| R3-241822 | Discussion on support of AI/ML enabled slicing | CATT |
| R3-241823 | (TP for TR 38.743 )Support of AI/ML enabled slicing | CATT |
| R3-241843 | (TP for TR 38.743) AI/ML Network Slicing for Rel-19 | Nokia, Telecom Italia |
| R3-241867 | Discussion on AI/ML assisted Network Slicing | ZTE |
| R3-241868 | (TP to TR38.743) AI/ML assisted Network Slicing | ZTE |
| R3-241941 | Discussion on AI-based network slice | CMCC |
| R3-241986 | Discussion on RAN AI/ML for Network Slicing | Huawei |
| R3-242065 | TP on AIML for Network Slicing | Ericsson, Charter, InterDigital, Telecom Italia |
| R3-242066 | AIML for Network Slicing | Ericsson, Charter, InterDigital, Telecom Italia |
| R3-242145 | CB:#AIRAN1_Slicing | ZTE |
| R3-242160 | (TP to TR38.743) AI/ML assisted Network Slicing | ZTE |
| R3-242233 | (TP to TR38.743) AI/ML assisted Network Slicing | ZTE, Nokia, Huawei, Samsung, Ericsson, CATT, Deutsche Telekom, CMCC, Telecom Italia |
| 11.3 | AI/ML enabled Coverage and Capacity Optimization | |
| R3-241566 | Discussion on use case of AIML enabled coverage and capacity optimization | China Telecommunication |
| R3-241567 | Discussion on use case of AIML enabled coverage and capacity optimization with existing NG-RAN architecture | China Telecommunication |
| R3-241591 | Considerations on AI/ML based CCO | NEC |
| R3-241592 | TP to TR38.743 for AI/ML based CCO | NEC |
| R3-241612 | Discussion on AI/ML enabled CCO | Qualcomm Incorporated |
| R3-241730 | (TP to TR 38.743) AI/ML enabled CCO | Samsung |
| R3-241793 | Discussion on AIML based CCO | Lenovo |
| R3-241794 | TP to 38.743 for AIML based CCO | Lenovo |
| R3-241824 | Discussion on support of AI/ML enabled CCO | CATT |
| R3-241825 | (TP for TR 38.743 )Support of AI/ML enabled CCO | CATT |
| R3-241829 | CCO Use case | InterDigital |
| R3-241842 | (TP for TR 38.743) Support of AI/ML-based CCO | Nokia |
| R3-241859 | Discussion on CCO considering AI/ML functionality | LG Electronics Inc. |
| R3-241869 | Discussion on AI/ML assisted Coverage and Capacity Optimization | ZTE |
| R3-241870 | (TP to TR38.743) AI/ML assisted Coverage and Capacity Optimization | ZTE |
| R3-241942 | Discussion on AI/ML-based CCO | CMCC |
| R3-241987 | Discussion on RAN AI/ML for Coverage and Capacity Optimization | Huawei |
| R3-242074 | TP on AIML support for CCO | Ericsson, Deutsche Telekom, Charter, Telecom Italia |
| R3-242075 | AIML support for CCO | Ericsson, Deutsche Telekom, Charter, Telecom Italia |
| R3-242146 | CB:#AIRAN2_CCO | Samsung |
| R3-242161 | (TP to TR 38.743) AI/ML enabled CCO | Samsung |
| R3-242231 | (TP to TR 38.743) AI/ML enabled CCO | Samsung, Ericsson, Huawei, Telecom Italia, ZTE, Nokia, CATT, Deutsche Telekom, LG Electronics, Telecom Italia |
| 11.4 | R18 leftovers | |
| R3-241593 | Considerations on AI/ML Rel-18 leftovers | NEC |
| R3-241594 | TP to TR38.743 for AIML Rel-18 leftovers | NEC |
| R3-241613 | Discussion on Continous MDT | Qualcomm Incorporated |
| R3-241614 | Discussion on Multihop UE Trajectory Prediction and Feedback | Qualcomm Incorporated |
| R3-241615 | AI/ML | Qualcomm Incorporated |
| R3-241731 | (TP to TR 38.743) AI/ML for mobility in NR-DC | Samsung |
| R3-241732 | (TP to TR 38.743) AI/ML for NG-RAN in split architecture | Samsung |
| R3-241733 | (TP to TR 38.743) Continuous MDT collection targeting the same UE across RRC states | Samsung |
| R3-241734 | (TP to TR 38.743) Multi-hop UE trajectory across gNBs | Samsung |
| R3-241795 | Discussion on Rel18 AIML for RAN left over issues | Lenovo |
| R3-241796 | TP to 38.743 for Rel18 AIML for RAN left over issues | Lenovo |
| R3-241826 | (TP for TR 38.743 )Support of AL/ML for NG-RAN in NR-DC scenario and Split architecture | CATT |
| R3-241827 | (TP for TR 38.743 )Support of multi-hop UE trajectory prediction/feedback | CATT |
| R3-241830 | Multi hop UE trajectory Feedback | InterDigital |
| R3-241844 | (TP for TR 38.743) AI/ML Mobility Optimization for NR-DC | Nokia |
| R3-241845 | (TP for TR 38.743) Split Architecture Support for the Rel-18 AI/ML Use Cases | Nokia |
| R3-241846 | AI/ML Energy Saving Discussion | Nokia, Deutsche Telekom, BT, Telecom Italia |
| R3-241847 | (TP for TR 38.743) AI/ML Energy Saving Enhancements | Nokia, Deutsche Telekom, BT, Telecom Italia |
| R3-241848 | (TP for TR 38.743) Continuous MDT Data Collection for Management-Based MDT | Nokia |
| R3-241849 | (TP for TR 38.743) AI/ML Multi-hop Trajectory | Nokia |
| R3-241871 | Discussion on Rel-18 Leftovers | ZTE |
| R3-241872 | (TP to TR38.743) Rel-18 Leftovers | ZTE |
| R3-241937 | Discussion on AI/ML based Mobility Optimization for NR-DC | CMCC |
| R3-241938 | Discussion on Multi-hop UE trajectory across gNBs | CMCC |
| R3-241943 | Further Discussion on AI/ML Network Energy Saving | CMCC |
| R3-241944 | Discussion on AI/ML for split architecture use cases | CMCC |
| R3-241988 | Rel-18 leftovers: AI/ML-based mobility enhancements | Huawei |
| R3-241989 | Split architecture support for Rel-18 "AI/ML for NG-RAN" use cases | Huawei |
| R3-241990 | Enhancements for the Rel-18 AI/ML-based Energy Saving use case | Huawei |
| R3-241991 | On Continuous MDT for AI/ML | Huawei |
| R3-242052 | Discussion on AIML energy cost prediction | NTT DOCOMO INC.. |
| R3-242067 | TP on multi-hops UE Trajectory | Ericsson |
| R3-242068 | Considerations on solutions for multi-hops UE Trajectory | Ericsson |
| R3-242072 | TP on AI/ML Network Energy Saving | Ericsson |
| R3-242073 | AI/ML Network Energy Saving | Ericsson |
| R3-242076 | TP on Mobility Optimization for NR-DC | Ericsson, InterDigital, Deutsche Telekom |
| R3-242077 | Mobility Optimization for NR-DC | Ericsson, InterDigital, Deutsche Telekom |
| R3-242147 | CB:#AIRAN3_R18Leftovers | Ericsson |
| R3-242228 | TP on multi-hops UE Trajectory | Ericsson, ZTE |
| R3-242229 | TP on Mobility Optimization for NR-DC | Ericsson, InterDigital, Deutsche Telekom |
| 12.1 | General | |
| R3-241622 | TR skeleton for additional topological enhancements for NR | NTT DOCOMO INC., AT&T |
| R3-241623 | Work plan for Additional topological enhancements | NTT DOCOMO INC., AT&T |
| R3-242242 | TR skeleton for additional topological enhancements for NR | NTT DOCOMO INC., AT&T |
| 12.2 | Wireless Access Backhaul (WAB) | |
| R3-241540 | (TP to TR 38.799) Architecture and protocol stack for WAB | CATT |
| R3-241541 | Discussion on impact of WAB mobility | CATT |
| R3-241542 | Discusson on operation and signling for supporting WAB | CATT |
| R3-241549 | Discussion on Network Selection for WAB | Fraunhofer IIS, Fraunhofer HHI |
| R3-241552 | Aspects related to WAB mobility and resource multiplexing | Qualcomm Inc. |
| R3-241553 | (TP to TR 38.799) Discussion on requirements for WAB | Qualcomm Inc. |
| R3-241554 | (TP to TR 38.799) Aspects related to WAB architecture | Qualcomm Inc. |
| R3-241601 | Discussion on the enhancements for WAB | NEC |
| R3-241625 | Discussion on Wireless Access Backhaul | NTT DOCOMO INC. |
| R3-241715 | Consideration on the architecture design for WAB | Huawei |
| R3-241716 | Consideration on the QoS support and mobility for WAB | Huawei |
| R3-241717 | Consideration on integration procedure and resource multiplexing for WAB | Huawei |
| R3-241743 | Discussion on architecture and protocol stack for WAB | Samsung |
| R3-241744 | Discussion on architecture requirement and deployment scenarios for WAB | Samsung |
| R3-241751 | (TP for TR 38.799) Architecture and protocol stack of MWAB | Xiaomi |
| R3-241752 | (TP for TR 38.799) Stage 2 procedures of MWAB | Xiaomi |
| R3-241781 | Architecture and Signalling Enhancements for Wireless Access Backhaul | China Telecom |
| R3-241797 | Architecture and protocol stacks of WAB node | Lenovo |
| R3-241798 | Discussion on integration and migration procedures for WAB node | Lenovo |
| R3-241799 | Discussion on resource multiplexing for WAB node | Lenovo |
| R3-241893 | Discussion on architecture and protocol stack for R19 WAB | ZTE |
| R3-241894 | Discussion on WAB mobility | ZTE |
| R3-241895 | Discussion on resource multiplexing and location service in WAB | ZTE |
| R3-241925 | (pCR for TR 38.799) WAB Architecture and Scenarios | Ericsson |
| R3-241926 | (pCR for TR 38.799) Functional Aspects of WAB-Nodes | Ericsson |
| R3-241927 | Handling of Reliability, Latency and Resource Multiplexing for WAB | Ericsson |
| R3-241979 | Discussion on support of WAB | LG Electronics |
| R3-241997 | Discussion on WAB architecture and high level aspects | Nokia, Nokia Shanghai Bell |
| R3-241998 | Discussion on WAB mobility and XnAP/NGAP impact | Nokia, Nokia Shanghai Bell |
| R3-241999 | Resource Multiplexing for WAB | Nokia, Nokia Shanghai Bell |
| R3-242151 | (TP to TR 38.799) WAB architecture and protocol stack | ZTE |
| R3-242152 | (TP to TR 38.799) WAB general requirements and architecture | NTTDOCOMO, INC. |
| R3-242156 | (TP to TR 38.799) WAB general requirements and architecture | NTTDOCOMO, INC. |
| R3-242159 | (TP to TR 38.799) WAB general requirements and architecture | NTTDOCOMO, INC. |
| R3-242236 | (TP to TR 38.799) WAB general requirements and architecture | NTTDOCOMO, Qualcomm, Ericsson, ZTE, Xiaomi, Huawei, Nokia, Nokia Shanghai Bell, Samsung, NEC, Fraunhofer, CATT |
| 12.3 | 5G Femto | |
| R3-241543 | (TP to TR 38.799) Discussion on 5G Femto architecture | CATT |
| R3-241544 | Discussion on 5G Femto local service access | CATT |
| R3-241545 | Discussion on 5G Femto access control mechanism | CATT |
| R3-241555 | (TP to TR 38.799) Discussion on requirements for 5G Femto | Qualcomm Inc. |
| R3-241556 | Architecture, access control and local services for 5G Femto | Qualcomm Inc. |
| R3-241565 | On 5G Femto Support | China Telecommunication |
| R3-241598 | Considerations on 5G femto | NEC |
| R3-241624 | Discussion on 5G Femto | NTT DOCOMO INC. |
| R3-241684 | Access to local services from the 5G Femto via collocated local UPF | Huawei |
| R3-241718 | Discussion on the architecture design for 5G femto | Huawei |
| R3-241719 | Discussion on the access control for 5G femto | Huawei |
| R3-241745 | Discussion on architecture and functional impact for Femto | Samsung |
| R3-241800 | Architecture and protocal stacks of 5G femto | Lenovo |
| R3-241801 | Access control and handover for 5G Femto with CAG | Lenovo |
| R3-241831 | Solution for 5G Femto Architecture | Nokia, TMO US, AT&T, Verizon Wireless, BT, NTT Docomo, KDDI |
| R3-241832 | [TP for TR 38.799] Solution for 5G Femto architecture | Nokia, TMO US, AT&T, Verizon Wireless, BT, NTT Docomo, KDDI |
| R3-241833 | [TP for TR 38.799] Initial Access Control of 5G Femtos | Nokia |
| R3-241834 | [TP for TR 38.799] Access Control of 5G Femtos for Mobility | Nokia |
| R3-241835 | LS on security aspect for handover to target 5G Femto | Nokia |
| R3-241896 | Discussion on RAN architecture and required functional for 5G femto | ZTE |
| R3-241897 | Discussion on access control for 5G femto | ZTE |
| R3-241898 | Discussion on local services for 5G femto | ZTE |
| R3-241980 | Discussion on support of 5G Femto | LG Electronics |
| R3-242040 | Femto Architecture and NG-RAN | Ericsson LM |
| R3-242041 | Access Control with CAG | Ericsson LM |
| R3-242042 | Access to Local Services via Local UPF | Ericsson LM |
| R3-242157 | (TP to TR 38.799) 5G Femto general requirements and architecture | NTTDOCOMO, INC. |
| R3-242158 | Summary of Offline Discussion on additional topological enhancement | NTTDOCOMO, INC. |
| R3-242164 | TP to TR38.799 for option1 | Huawei |
| R3-242165 | TP to TR38.799 for option2 | Nokia |
| R3-242166 | TP to TR38.799 for Option3 | Ericsson |
| R3-242167 | TP to TR38.799 for Option4 | Samsung |
| R3-242237 | TP to TR38.799 for option1 | Huawei, ZTE |
| R3-242238 | TP to TR38.799 for option2 | Nokia, TMO US, AT&T, Verizon Wireless, BT, NTT Docomo, KDDI, Charter |
| R3-242239 | TP to TR38.799 for Option3 | Ericsson |
| R3-242240 | TP to TR38.799 for Option4 | Samsung |
| 13.1 | General | |
| R3-241889 | Work plan for Rel-19 Further NR Mobility Enhancements | China Telecom, Apple Inc. |
| 13.2 | Support for inter-CU LTM | |
| R3-241527 | Discussion on Inter-gNB-CU LTM Procedure | Nokia |
| R3-241528 | Discussion on Inter-gNB-CU LTM via NG Interface | Nokia |
| R3-241529 | Discussion on LTM when NR-DC is Configured | Nokia |
| R3-241532 | Design considerations to support inter-gNB LTM HO | Qualcomm Incorporated |
| R3-241603 | Consideration impact on Xn for inter-CU LTM | NEC |
| R3-241724 | Scope clarification to Rel-19 mobility enhancement WI | Huawei |
| R3-241725 | (TP for LTM BLCR for TS38.300): Inter-CU LTM basic procedure | Huawei |
| R3-241726 | Discussion on subsequent inter-CU LTM | Huawei |
| R3-241758 | Discussion on the scenario for Inter-CU LTM | CATT |
| R3-241759 | Initial thought for Inter-CU LTM candidate cells preparation | CATT |
| R3-241760 | Discussion on synchronize among candidate cells | CATT |
| R3-241802 | General aspects of inter-CU LTM | Lenovo |
| R3-241803 | TP to inter-CU LTM for TS38.423 | Lenovo |
| R3-241804 | Security considerations of inter-CU LTM | Lenovo |
| R3-241819 | Scenarios for inter-CU LTM | Ericsson |
| R3-241820 | High level design principle for inter-CU LTM | Ericsson |
| R3-241821 | Details of XnAP signaling design | Ericsson |
| R3-241890 | Discussion on applicable scenarios for inter-CU LTM | China Telecom |
| R3-241891 | Discussion on signaling enhancement for inter-CU LTM | China Telecom, Apple Inc. |
| R3-241892 | Discussion on data forwarding and security key handling for inter-CU LTM | China Telecom |
| R3-241899 | Discussion on inter-CU LTM | ZTE |
| R3-241900 | (TP to TS 38.423) Support of inter-CU LTM | ZTE |
| R3-241901 | (BL CR to 38.420) Introduction of inter-CU LTM | ZTE |
| R3-241956 | Initial Considerations on inter-CU LTM | CMCC |
| R3-241963 | Discussion on Inter-CU LTM | Samsung |
| R3-241964 | (TP to BLCR for TS 38.423) Xn impact for Inter-CU LTM | Samsung |
| R3-241965 | (TP to BLCR for TS 38.401/38.300) Procedure for Inter-CU/gNB LTM | Samsung |
| R3-242053 | Discussion on inter-CU LTM | NTT DOCOMO INC.. |
| R3-242096 | High-level principles and discussions for Inter-CU LTM signaling design | LG Electronics Inc. |
| R3-242097 | Baseline CR for introducing Rel-19 Mobility enhancement in E1AP | LG Electronics Inc. |
| R3-242098 | High-level principles for Inter-CU LTM security master key handling | LG Electronics Inc. |
| 14.1 | General | |
| R3-241930 | Work plan for Rel-19 NR_NTN_Ph3 | CATT, Thales |
| 14.2 | Support MBS broadcast service | |
| R3-241562 | Discussion on MBS service in NTN system | CAICT |
| R3-241568 | MBS support in NR NTN | China Telecommunication |
| R3-241606 | Discussion on Support for NR NTN MBS Broadcast Service | Qualcomm Incorporated |
| R3-241617 | Discussion on Support of MBS Broadcast over NTN access | TCL |
| R3-241749 | (TP to TS 38.413) Support of Broadcast service | Xiaomi |
| R3-241805 | On support of MBS broadcast in NTN | Lenovo |
| R3-241908 | (TP for TS 38.413 and TS 38.300) Support MBS broadcast service | Huawei |
| R3-241931 | Discussion on MBS broadcast service for NR NTN system | CATT, CBN, China Broadnet |
| R3-241946 | Discussion on Supporting MBS broadcast service for NR NTN | CMCC |
| R3-242036 | Discussion on support MBS broadcast service for NR NTN | Samsung |
| R3-242043 | Service Area for a Broadcast Service in NR NTN | Ericsson, Thales |
| R3-242080 | Discussion on NTN MBS supporting | ZTE |
| 14.3 | Support of Regenerative payload | |
| R3-241569 | Consideration on regenerative payload in Rel-19 NTN | China Telecommunication |
| R3-241582 | Discussion on support of Regenerative payload | NEC |
| R3-241607 | Discussion on NG Signaling impacts for NR NTN Regenerative Payload | Qualcomm Incorporated |
| R3-241616 | Discussion on Support of NTN Regenerative Architecture | TCL |
| R3-241750 | Discussion on Support of Regenerative Payload | Xiaomi |
| R3-241770 | Initial Considerations on Support of Regenerative Payload | ZTE |
| R3-241806 | On support of regenerative payload in NTN | Lenovo |
| R3-241909 | Support of Regenerative payload | Huawei |
| R3-241932 | Discussion on support of regenerative payload | CATT |
| R3-241947 | Discussion on Support of regenerative payload for NR NTN | CMCC |
| R3-242000 | Discussion on the support of Regenerative payload | Nokia, Nokia Shanghai Bell |
| R3-242001 | Support Regenerative NTN | Nokia, Nokia Shanghai Bell |
| R3-242037 | Discussion on support of regenerative payload for NR NTN | Samsung |
| R3-242044 | Support for Regenerative Payload in NR NTN | Ericsson, Thales, Deutsche Telekom, Nokia |
| R3-242045 | NTN Regenerative Payload in Rel-19 | Ericsson LM |
| R3-242099 | Satellite on-board gNB identification in 5G system | LG Electronics Inc. |
| R3-242100 | CR for Satellite on-board gNB identification in 5G system | LG Electronics Inc. |
| R3-242172 | CB:#NRNTN_Archtecture | Ericsson |
| R3-242232 | CB:#NRNTN_Archtecture | Ericsson |
| 16.1 | General | |
| R3-241679 | TR 38.769 skeleton for Study on solutions for Ambient IoT (Internet of Things) in NR | Huawei, CMCC |
| R3-241957 | Work Plan for Ambient IoT SI | CMCC, Huawei, T-Mobile USA |
| R3-242148 | TR 38.769 skeleton for Study on solutions for Ambient IoT (Internet of Things) in NR | Huawei, CMCC |
| 16.2 | RAN Architecture | |
| R3-241570 | Initial views on RAN architecture for Ambient IoT | China Telecommunication |
| R3-241583 | Discussion on A-IoT RAN architecture | NEC |
| R3-241635 | On Requirements and Use Cases in Ambient IoT study in 3GPP Rel-19 | Ericsson |
| R3-241636 | On Use Cases for Ambient IoT work in 3GPP Rel-19 and related functions | Ericsson |
| R3-241638 | Flows and Time Lines for Ambient IoT study in 3GPP Rel-19 | Ericsson |
| R3-241680 | RAN architecture aspects for Ambient IoT | Huawei |
| R3-241746 | Discussion on AIoT RAN architecture | Xiaomi |
| R3-241807 | RAN architecture considerations of ambient IoT | Lenovo |
| R3-241836 | [TP for TR 38.769] Architecture Requirements for Supporting Ambient AIoT Devices | Nokia |
| R3-241837 | [TP for TR 38.769] RAN Architecture and Protocol Stack for AIoT | Nokia |
| R3-241850 | Architecture aspects and Protocol stack for Ambient IoT | Qualcomm Incorporated |
| R3-241933 | Consideration on A-IoT architecture aspects | CATT |
| R3-241958 | Discussion on RAN Architecture for Ambient IoT | CMCC |
| R3-241981 | Discussion on RAN architecture for Ambient IoT | LG Electronics |
| R3-242038 | Discussion on RAN architecture for Ambient IoT | Samsung |
| R3-242087 | Discussion on RAN architecture for Ambient-IOT | ZTE |
| R3-242149 | CB:#AIoT1_General | Huawei |
| 16.3 | RAN-CN Interface Impact | |
| R3-241584 | Discussion on A-IoT NG RAN interface impact | NEC |
| R3-241637 | RAN-CN Protocol Aspects for Ambient IoT study in 3GPP Rel-19 | Ericsson |
| R3-241681 | Inventory over CN-RAN interface | Huawei |
| R3-241682 | Data Transport and Device context management over CN-RAN interface | Huawei |
| R3-241747 | (TP for TR 38.769) AIoT interface impacts between RAN and CN | Xiaomi |
| R3-241808 | Paging considerations of ambient IoT | Lenovo |
| R3-241809 | Device context management considerations of ambient IoT | Lenovo |
| R3-241810 | Data transport considerations of ambient IoT | Lenovo |
| R3-241838 | Paging Signalling Impacts for AIoT | Nokia |
| R3-241839 | [TP for TR 38.769] Paging Signalling Impacts for AIoT | Nokia |
| R3-241851 | Paging and device context management for Ambient IoT | Qualcomm Incorporated |
| R3-241905 | Discussion on NG Interface Signalling for Ambient IoT | China Telecom |
| R3-241934 | Discussion on Paging for A-IoT | CATT |
| R3-241935 | Discussion on UE context management and Data transport for A-IoT | CATT |
| R3-241959 | Discussion on paging for Ambient IoT | CMCC |
| R3-241960 | Discussion on Device Context Management and Data Transfer | CMCC |
| R3-242039 | Discussion on RAN-CN interface impact for Ambient IoT | Samsung |
| R3-242088 | Discussion on NG interface impact for Ambient-IOT | ZTE |
| R3-242089 | Discussion on overall procedure for Ambient-IOT | ZTE |
| 16.4 | Others | |
| R3-241683 | Location report of Ambient IoT devices | Huawei |
| R3-241748 | (TP for TR 38.796) AIoT device localization | Xiaomi |
| R3-241852 | Ambient IoT positioning | Qualcomm Incorporated |
| R3-241936 | Consideration on positioning aspects for A-IoT | CATT |
| R3-241961 | Discussion on locating Ambient IoT device | CMCC |
| R3-242090 | Discussion on position for Ambient-IOT | ZTE |
| R3-242153 | CB:#AIoT2_Locating | CMCC |
| 17.1 | General | |
| R3-241651 | WI Work plan for R19 Network Energy Savings | Ericsson |
| 17.2 | Support on-demand SSB SCell operation | |
| R3-241546 | Discussion on on-demand SSB for SCell | CATT |
| R3-241656 | On-demand SSB SCell operation | Ericsson |
| R3-241685 | Discussion on on-demand SSB SCell operation | Huawei |
| R3-241735 | Discussion on on-demand SSB SCell operation | Samsung |
| R3-241811 | Disucusion on On-demand SSB for SCell | Lenovo |
| R3-241840 | Considerations on On-Demand SSB SCell operation for UEs in connected mode | Nokia |
| R3-242056 | Discussion on on-demand SSB Scell operation | ZTE |
| 17.3 | Support on-demand SIB1 for UEs | |
| R3-241547 | Discussion on support on-demand SIB1 for UE | CATT |
| R3-241596 | SIB1 transmission of a NES cell | NEC |
| R3-241597 | CR to 38.000 on inter-node exchange of UL WUS configuration | NEC |
| R3-241657 | On-demand SIB1 transmission | Ericsson |
| R3-241686 | (TP for TS 38.473) Discussion on on-demand SIB1 for UEs | Huawei |
| R3-241736 | Discussion on on-demand SIB1 | Samsung |
| R3-241812 | Disucusion on On-demand SIB1 for Idle/Inactive UE | Lenovo |
| R3-241841 | Considerations on On-Demand SIB1 Support | Nokia |
| R3-241949 | Discussion on On-Demand SIB1 | CMCC |
| R3-241950 | Discussion on Activation and Deactivation of ON-Demand SIB1 Request Configuration Broadcast | CMCC |
| R3-242057 | Discussion on on-demand SIB1 for idle/inactive mode UEs | ZTE |
| 19.1 | General | |
| R3-242063 | Work plan for WI on Full Duplex | Huawei, Samsung |
| 21.1 | General | |
| R3-242002 | Work Plan for Rel-19 on XR Enhancements for NR | Nokia, Qualcomm (Rapporteurs) |
| 21.2 | Support XR in DC | |
| R3-241576 | Signaling Enhancements to support UL PSI based discarding and UL BAT reporting for XR DC | Qualcomm Incorporated |
| R3-241577 | XR DC Signaling Enhancements to support ECN marking and congestion reporting | Qualcomm Incorporated |
| R3-241581 | Support of XR in DC | NEC |
| R3-241647 | UL BAT transmission in unsynchronized network | Ericsson |
| R3-241720 | Enhancement for NR-DC support of XR | Huawei |
| R3-241721 | Enhancement for NR-DC support of XR | Huawei |
| R3-241741 | Discussion on support XR in DC | Samsung |
| R3-241742 | Support XR in DC | Samsung |
| R3-241813 | ECN Marking and Congestion Reporting in NR-DC | Lenovo |
| R3-241814 | PDU Set handling, BAT and PSI based discard coordination in NR-DC | Lenovo |
| R3-241902 | Discussion on support XR in DC | ZTE |
| R3-241903 | (TP to TS 38.423 and 37.340) Support of XR in DC | ZTE |
| R3-241951 | Discussion on ECN Marking in Multi-Radio Dual Connectivity (MR-DC) Scenarios | CMCC |
| R3-241952 | Discussion on PSI Discard coordination in Multi-Radio Dual Connectivity (MR-DC) Scenarios | CMCC |
| R3-242003 | Discussion on the support of XR in NR-NR DC | Nokia, Nokia Shanghai Bell |
| R3-242004 | Introduction the support XR in DC | Nokia, Nokia Shanghai Bell |
| R3-242012 | Discussion on XR in DC | CATT |
| R3-242013 | Support on XR in DC | CATT |
| R3-242101 | Support for L4S in DC | Ericsson, Deutsche Telekom, Charter |
| R3-242102 | Support for L4S in NR-NR DC | Ericsson, Deutsche Telekom, Charter |
| R3-242154 | CB:#R19XR | Lenovo |
| R3-242192 | Support of XR enhancements | ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi |
| R3-242202 | Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm |
| R3-242234 | Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei |
| R3-242241 | Support of XR enhancements | CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC |